This repository has been archived by the owner on Feb 7, 2022. It is now read-only.
Setup tests #6
Open
Setup tests #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is my take on setup testing for the backend. I split up a lot of logic in smaller chunks to allow better unit tests. I also wrote some tests for some utility functions.
you can run the tests and see the (low) coverage by running
npm t -- --coverageThe frontend still needs some kind of bundler to make it more testable (IMHO).
The idea would be to move the
jest.config.jsand the currentpackage.jsonto thebackendfolder and create a new testing environment for thefrontendin theclientfolder.Let me know what you think.